Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

added .npmignore file #42

Merged
merged 1 commit into from
Jul 24, 2015
Merged

added .npmignore file #42

merged 1 commit into from
Jul 24, 2015

Conversation

PavelVanecek
Copy link
Contributor

including the test/ folder to .npmignore means it will not be downloaded on npm install. This has two advantages:

  1. less data to download on npm install
  2. when developing a google chrome extension, a warning pops out, saying This extension includes the key file '.../node-rsa/test/private_pkcs1.pem'. You probably don't want to do that. There is no security threat since the key is not used anyway; the npmignore just gets rid of the warning.

More info about .npmignore: https://docs.npmjs.com/misc/developers#keeping-files-out-of-your-package

Has been done in thom4parisot/crx#47

including the test/ folder to .npmignore means it will not be downloaded on npm install. This has two advantages:

1. less data to download on `npm install`
2. when developing a google chrome extension, a warning pops out, saying *This extension includes the key file '.../node-rsa/test/private_pkcs1.pem'. You probably don't want to do that.* There is no security threat since the key is not used anyway; the npmignore just gets rid of the warning.
rzcoder added a commit that referenced this pull request Jul 24, 2015
@rzcoder rzcoder merged commit 54fcd4a into rzcoder:master Jul 24, 2015
@rzcoder
Copy link
Owner

rzcoder commented Jul 24, 2015

Thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants